History

----
3.54
----
COM40.SYS, like COM.SYS, drops DTR when the com device is closed.
PCBoard2 BBS closes the com device whenever it shells out to do
most things (one exception).  This results in a lost connection
(DTR dropped usually results in the modem losing carrier, i.e.,
hanging up).  COM40.SYS version 3.52 (and later) now leave the MCR
as-is, so no DTR drop, and no lost connection (requires -mcr as
first-instance switch).

New command-line switches:

 -mcr    leave DTR as-is when device closed (first instance switch)

Second-instance switches:

 -mcr:asis   reinstate DTR as-is (do not drop when device closed)
 -mcr:drop   drop DTR/RTS when device is next closed


- AWACS.EXE     3.54
- COM40.SYS     3.52
- AWACS.DOC     updated


----
3.53
----

AWACS would do a quick-exit if the CID was in a closed state
rather than a full-exit, when shutdown.  Working set info
has more info shown:  "accs" is total memory accessed since
last reset (default is every 120 periods (use -rst: to change
number of periods, and Wks timer interval the length of
each period)); "peak" is the max "accs" value encountered.
Peak (and accs) can be reset by clicking the radio button
next to Working Set in the PM control box (in some cases
click twice).

- AWACS.EXE     3.53


----
3.52
----
AWACS would periodically let a caller ID stream get past
without displaying it.

Updated program files are:

- AWACS.EXE     3.52
- COM40.SYS     3.51


----
3.51
----
AWACS no longer needs to own the com device for caller ID
info to display, which allows it to be used on a machine
with a BBS running.  The only time the com port needs to be
owned by AWACS is when it first initializes.  Thereafter, no
matter who owns the modem port, caller ID info is displayed in
real-time.  Com port stats are available at all times, as
before.  (Someone must have the com port open, though, either
AWACS or some other program, like PCBoard BBS for example,
and must have the caller ID init string sent to the modem,
usually AT#CID=2.)

The ideal system would be an OS/2 machine with a caller ID
modem (and telco service), a BBS running, and MDA hardware.
AWACS can also work just fine on a system without a modem,
without MDA hardware, in which case you can still monitor
the swap file size/used, working set, system memory, pulse,
and time, and even com port stats, to a PM window on the
desktop (see -cHeight switch).

Updated program files are:

- AWACS.EXE     3.51
- MONYiii.SYS   3.50
- COM40.SYS     3.50
- AWACS.DOC     updated


----
3.47
----
Added a new caller ID feature (see awacs.doc).  Improved
accuracy of the pulse tick by calibrating for a full second
rather than a quarter-second.  The original CID priority is
reinstated after a -close/-open.  The updated package files
are AWACS.EXE and AWACS.DOC.

Updated program files are:

- AWACS.EXE     3.47
- AWACS.DOC     updated


----
3.46
----
Theseus2 is now used for working set analysis only, with
the swap file analysis performed by the Mony driver. The
next AWACS (4.00) will wean itself from Theseus2 entirely
by having home-grown code do the working set and locked
memory stats (and -much- more efficiently).

Updated program files are:

- AWACS.EXE     3.45
- MONYiii.SYS   3.45
- COM40.SYS     3.01
- MONYPAGE.EXE  updated
- AWACS.DOC     updated


----
3.01
----
Version 3.00 (unregistered) could hang the OS if AWACS
was run longer than 2 hours or so after an OS boot.

Update program files are:

- AWACS.EXE     3.01


----
3.00
----
See the awacs.doc file for what you need to know.
This is the initial, hence beta, release of AWACS 3.0,
but it should be reasonably well-behaved.  If not,
send gripes and moans to the address in the .doc file.


